2014-05-01 - 12514 - Spec - L86,S01 MSRP - NEW #SDLABELREPORTS #US #abapidoc #abapexit

SPECIFICATIONS

12514 - Spec - L86,S01 MSRP

Purpose

To pass ZMRP and its value to the outbound IDOC if the VAS codes are L86 and S01 in the sales order and over write the ZCRS value.

Admin Info

Purpose	To pass ZMRP and its value to the outbound IDOC if the VAS codes are L86 and S01 in the sales order and over write the ZCRS value.
Requested By	Lizz Paxson
Spec Created By	Deepak Yasam
Spec Created Date	05/01/2014
Spec QA by	Deepak Yasam
Objects	ZXTRKU02
Document Status	Completed

Estimates

Sl.	Activity	Estimation in Hours
1	Research	08
2	Documentation	08
3	Development/ Config	40
4	Unit test in DEV	20
5	Unit test in QUA	20
6	Other activity
	TOTAL	96

References

Prior Tickets

[Provide links of prior associated Spec / Break Fix BOSS document(s)]

None

Documents

[Attach any document(s) received for the requirement(s)]

None

Spec Changes

[List the changes made to program after the approval of the original requirement along with the Date on which change request received and the name of the initiator]

Sl.	Change Details	Requested By	Requested On	Notes if any
1	Carry out changes for the inbound delivery IDOC as well	Lizz Paxon	04/21/2014	Original requirement was for outbound delivery IDOC only; BMS recommended changes for inbound delivery IDOC.

Functional Requirement

Purpose/WHY:

[Explain the purpose of the project and the reason why this requirement has come]

Pass ZMRP and its corresponding value to the outbound IDOC segment Z1REFORDP01 if the VAS codes are L86 and S01 in the sales order and over write the ZCRS value. This should affect both inbound and outbound deliveries.
Following are the conditions if the VAS codes are L86,S01 and

if the document has ZMRP then the ZMRP value should be dispalyed in the IDOC
If the document has both ZMRP and ZCRS then only ZMRP value should be dispalyed in the IDOC
If the document doesn't have ZMRP and has ZCRS alone then what should be displayed in the IDOC. This should fail.

In Scope:

[List the activities to be included in scope]

The requirement is applicable for Labels L86 and S01 only. IDOC's for both Inbound and Outbound deliveries will be impacted.

Out of Scope:

[Out of scope activities]

All other Labels and/or combinations are not included in this development and the values passed to the IDOC segment Z1REFORDP01 will not be affected.

Solution Summary

[Discuss this section with Requester and get approval prior to beginning work]

The development changes needs to be done in the include ZXTRKU02 to pass the ZMRP values into the outbound IDOC in the delivery document if the VAS codes are L86 and S01 in the sales order.
As both the message types DESADV and WHSORD has common extension ZXDELVRY03,the ZMRP changes will affect both the message types.So if we make the ZMRP changes for only WHSORD then it will apply for outbound delivery but not for inbound as it uses DESADV ie ASN for customer.

Below are the output types for the outbound and inbound deliveries that contains the above changes.
ZLD4 - Outbound
ZASN - Inbound.

Test Plan

[List test scenarios/cases to be executed here]

For Inbound deliveries:
Scenarios with L86 + S01 in the sales order:

Sl.	Test Scenario	Expected Result
1	Create SO with ZMRP pricing condition and issue ZASN output in inboun delivery.	The segment Z1REFORDP01 should display ZMRP (KSCHL2) and its value (KBETR2) along with J3AP values.
2	Create SO with ZMRP and ZCRS and issue ZASN output in inbound delivery.	The segment Z1REFORDP01 should display ZMRP (KSCHL2) and its value (KBETR2) along with J3AP values.
3	Create SO with no ZMRP/ ZCRS and issue ZASN output in inbound delivery.	The segment Z1REFORDP01 should display only J3AP values.
4	Create SO with ZCRS and issue ZASN output in inbound delivery.	The segment Z1REFORDP01 should display only J3AP values.

Scenarios other than L86 and S01 in the sales order:

Sl.	Test Scenario	Expected Result
5	Create SO with ZMRP and issue ZASN output in inbound delivery.	The segment Z1REFORDP01 should display only J3AP values.
6	Create SO with ZMRP and ZCRS and issue ZASN output in inbound delivery.	The segment Z1REFORDP01 should display ZCRS values along with J3AP values.
7	Create SO with no ZMRP/ ZCRS and issue ZASN output in inbound delivery.	The segment Z1REFORDP01 should display only J3AP values
8	Create SO with ZCRS and issue ZASN output in inbound delivery.	The segment Z1REFORDP01 should display ZCRS values along with J3AP values.

For Outbound deliveries:

Scenarios with L86 + S01 in the sales order:

Sl.	Test Scenario	Expected Result
1	Create SO with ZMRP pricing condition and issue ZLD4 output in delivery.	The segment Z1REFORDP01 should display ZMRP (KSCHL2) and its value (KBETR2) along with J3AP values.
2	Create SO with ZMRP and ZCRS and issue ZLD4 output in delivery.	The segment Z1REFORDP01 should display ZMRP (KSCHL2) and its value (KBETR2) along with J3AP values.
3	Create SO with no ZMRP/ ZCRS and issue ZLD4 output in delivery.	The segment Z1REFORDP01 should display only J3AP values.
4	Create SO with ZCRS and issue ZLD4 output in delivery.	The segment Z1REFORDP01 should display only J3AP values.

Scenarios other than L86 and S01 in the sales order:

S.Lno	Test Scenario	Expected Result
5	Create SO with ZMRP and issue ZLD4 output in delivery.	The segment Z1REFORDP01 should display only J3AP values.
6	Create SO with ZMRP and ZCRS and issue ZLD4 output in delivery.	The segment Z1REFORDP01 should display ZCRS values along with J3AP values.
7	Create SO with no ZMRP/ ZCRS and issue ZLD4 output in delivery.	The segment Z1REFORDP01 should display only J3AP values
8	Create SO with ZCRS and issue ZLD4 output in delivery.	The segment Z1REFORDP01 should display ZCRS values along with J3AP values.

Solution Details

In the Userexit (ZXTRKU02) for the Delivery Segment type 'E1EDL24' ; if the Delivery Type VBTYP is 'EL'.
Then Populate the ZMRP Pricing Condition in segmnt-Z1REFORDP01.
If the VAS codes are L86 and S01 then eliminate ZCRS pricing condition for both outbound and inbound delivery.

Issues

[List Issues / Bugs identified in configuration or development]

None